CronniX 3.0 Release Notes
Oktober 25, 2004
Version 3.0 is a major update with the following changes
3.0b3
- Fixed parsing bug: User column of system crontab was ignored
- Fixed parsing bug: '=' sign in command string caused tasks to be read in a environment variables
- Fixed display issue: Info text field was not updated after deletes
3.0b2
- Fixed column resizing in the English version
- Updated Japanese localization (thanks to Yuzuru Shiraiwa for the update)
- Updated French localization (thanks to MichaĆl Ghez, Claude Tamone, Damien Bobillot for their contributions. I've included Damien's translations as it was the latest -- in order to prevent folks from independently translating CronniX please always check back with me if there's an updated localized variant that's not released yet. There have been several occasions where I had to choose between translations and believe me there's little justice I can do your fine work with most of the languages you translate CronniX to :))
- Included all remaining localizations
3.0b1
- New crontab parsing: preserving unknown/unparsable content
- Drag and drop of tasks and environment variables (within CronniX and cross applications)
CronniX Help
The CronniX documentation is available from the Help menu in the application as well as on the CronniX website:
CronniX Help on the web
Known Problems
- Large crontabs: There's been a case where CronniX failed to save a very large (141 lines, 13 kB) crontab. I believe to know the cause of this, but fixing it will take some time. In the meantime, try to group entries by making intervals like '*/5' instead of having 12 entries for a minute of 0,5,10,... (as was the case in the problematic crontab) if possible. Reducing the crontab to a size below 8192 bytes (typically some 80-90 lines) will allow CronniX to read and write your crontab again. Sorry for the inconvenience. (See the FAQ for hints on how to save, view or remove your crontab from the command line.)
- If you open another user's crontab, be aware that the "Run Now" command will not execute the command as that user. They will always run as the current user. Therefore running the maintenance tasks in the system crontab as a regular user (even an administrator) will not do anything (not even harm :-) right now.
Support Development
CronniX is free and remains free. You can support its future development by making a credit card / PayPal donation. Please see
http://www.abstracture.de/cronnix/donate.html
for details. I'd appreciate it a lot if you'd have a look.
Localization
Please head to the localization section if you want to translate CronniX to your language.
Outlook / Next Version
Here's what I have planned for a future release:
- Preferences
- "Run Now" improvement (sudo for other users, better error reporting)
- Perform sanity checks before installing a crontab
- React to future user suggestions
Home